Skip to content

Add check_spike_times_without_nans#689

Open
h-mayorquin wants to merge 6 commits intodevfrom
deal_with_nan_in_spike_times
Open

Add check_spike_times_without_nans#689
h-mayorquin wants to merge 6 commits intodevfrom
deal_with_nan_in_spike_times

Conversation

@h-mayorquin
Copy link
Copy Markdown
Collaborator

Spike times are physical event timestamps representing when action potentials occurred. A spike either happened at a specific time or it didn't, so NaN is never a meaningful value. NaN in spike times typically indicates a conversion bug or array padding that was not cleaned up before writing to NWB.

Unlike other spike time checks that sample the first N elements, this check scans the full array because NaN values can appear at any position in the data.

@h-mayorquin h-mayorquin self-assigned this Mar 24, 2026
@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.12%. Comparing base (60bfe7f) to head (3144a11).
⚠️ Report is 1 commits behind head on dev.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##              dev     #689      +/-   ##
==========================================
+ Coverage   79.87%   83.12%   +3.25%     
==========================================
  Files          48       48              
  Lines        1873     1885      +12     
==========================================
+ Hits         1496     1567      +71     
+ Misses        377      318      -59     
Files with missing lines Coverage Δ
src/nwbinspector/checks/__init__.py 100.00% <ø> (ø)
src/nwbinspector/checks/_ecephys.py 94.35% <100.00%> (+0.41%) ⬆️

... and 5 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bendichter was this added accidentally?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants